…md ao atingir 5+

Estabelece regra operacional de governança de pipelines longos:

- Threshold: 5+ handoffs YAML para mesmo pipeline → MUST consolidar
- RUN-LOG.md vai em docs/stories/epics/{epic}/RUN-LOG.md (preferred)
- Handoff mais recente sempre fica individual (next session reads first)
- Originais arquivados em .aiox/handoffs/_archive/ (default)
- Preserva: contexto estratégico, ADRs, blockers resolvidos, schema changes
- Descarta: investigation steps, alternativas rejeitadas, tool sequences

Trigger desta sessão: pipeline meta-messaging Wave 1 → Wave 2 transition.
Mirror em business-ai-first/.claude/rules/handoff-consolidation.md (PR #59).

Atualiza CLAUDE.md (tabela de rules) com referência à nova regra.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

)

Establishes formal AIOX framework R&D pipeline triggered by Wave 1.A
correction in business-ai-first that exposed two systemic gaps:

1. No formal route for project-level audit findings to evolve framework
2. @aiox-master orchestrator has no triage.routing_matrix to consult
   specialized squads first when topic matches their domain

## What this PR adds

### audits/
- README.md — folder doctrine
- c-dev-organization-2026-05-07.md — narrative audit of C:/dev workspace
- promoted/AF-20260507-vocabulary-contract-failure.yaml — finding
- promoted/AF-20260507-aiox-master-routing-gap.yaml — finding

### governance/
- README.md — folder index
- evolution-pipeline.md — formal R&D pipeline spec (audit -> proposal -> Eliel approval -> PR)
- squad-activation-strategy.md — conditional consult-squad-first routing
- templates/audit-finding-tmpl.yaml — AuditFinding template
- templates/framework-proposal-tmpl.yaml — FrameworkProposal template
- proposals/README.md — proposal lifecycle doc
- proposals/PROP-20260507-vocabulary-contract.yaml — pending Eliel approval
- proposals/PROP-20260507-squad-routing-strategy.yaml — pending Eliel approval
- patterns/README.md — pattern catalog (catalog scaffold)

## Why this matters

Without the pipeline, every project re-discovers the same lessons,
voice-clone squads stay dormant, claude-code-mastery never gets invoked
from outside, and tokens burn on context redundancy. Eliel's diagnostic:
"todos os plans criados cogitaram em nenhum momento a perfeita
integração desses squads".

The pipeline is the discipline; the routing matrix is the mechanism.

## What this PR does NOT do (deferred to follow-up PRs after approval)

- Patch aiox-master.md to add triage block (separate PR per proposal approval)
- Add aiox-core/hooks/migration-dictionary-guard.cjs (separate PR)
- Add aiox-core/hooks/squad-suggestion-advisor.cjs (separate PR)
- Constitution amendment Article VII (separate PR)

This PR is governance-only. Implementation follows once Eliel signs the
two pending proposals.

## Authority

- Authors: @aiox-master (Orion) on Eliel's request
- Approver of governance content: Eliel (sole orchestrator approver)
- Reference: voice-clone formal opinions captured in business-ai-first
  ADR-DBOPS-V1-vocabulary-contract-failure.md

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

Eliel approved both proposals on 2026-05-07T19:15:00Z:

- PROP-20260507-vocabulary-contract: APPROVED
  Closes Akita's Article VII gap. Generalizes migration-dictionary-guard
  hook from business-ai-first project-local copy to framework. Prevents
  Wave 1.A failure mode (V1 reverted) in any future AIOX project.

- PROP-20260507-squad-routing-strategy: APPROVED
  Adds triage.routing_matrix to @aiox-master. Advisory hook suggests
  squads (voice-clones, claude-code-mastery, audience-engine, db-inventory)
  by keyword match. Closes Eliel-declared squad integration gap.

Implementation order: vocabulary-contract first, then squad-routing
references Article VII once formalized.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…oved